Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #3234

/assign sebsoto

We are reporting jobs as failed if a pod within the job failed. This is
incorrect logic, as a single pod failing is not a failure state for the
entire job. The job will keep creating pods until a success is seen.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60967 has been cloned as Jira Issue OCPBUGS-62480. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-62480: Fix job success logic

In response to this:

This is an automated cherry-pick of #3234

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-60967: Fix job success logic [release-4.18] OCPBUGS-62480: Fix job success logic Sep 30, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 30, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-62480, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-60967 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-60967 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #3234

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sebsoto
Copy link
Contributor

sebsoto commented Sep 30, 2025

/approve

@sebsoto
Copy link
Contributor

sebsoto commented Sep 30, 2025

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sebsoto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 30, 2025
@jrvaldes
Copy link
Contributor

/lgtm

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4a8da4c and 2 for PR HEAD daf778c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c159ae6 and 1 for PR HEAD daf778c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6382ba1 and 0 for PR HEAD daf778c in total

@openshift-ci-robot
Copy link

/hold

Revision daf778c was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 30, 2025
@sebsoto
Copy link
Contributor

sebsoto commented Oct 1, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2025
@sebsoto
Copy link
Contributor

sebsoto commented Oct 1, 2025

/override ci/prow/vsphere-disconnected-e2e-operator ci/prow/aws-e2e-operator

@sebsoto
Copy link
Contributor

sebsoto commented Oct 1, 2025

/cherry-pick release-4.17 release-4.16

@openshift-cherrypick-robot
Copy link
Author

@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17 release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 1, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/aws-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator

In response to this:

/override ci/prow/vsphere-disconnected-e2e-operator ci/prow/aws-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2896d06 and 2 for PR HEAD daf778c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7a61ec8 and 1 for PR HEAD daf778c in total

@sebsoto
Copy link
Contributor

sebsoto commented Oct 2, 2025

/override ci/prow/vsphere-proxy-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/vsphere-proxy-e2e-operator

In response to this:

/override ci/prow/vsphere-proxy-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6ccb122 and 0 for PR HEAD daf778c in total

@openshift-ci-robot
Copy link

/hold

Revision daf778c was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 7, 2025
@sebsoto
Copy link
Contributor

sebsoto commented Oct 9, 2025

/hold cancel

@sebsoto
Copy link
Contributor

sebsoto commented Oct 9, 2025

/override ci/prow/platform-none-vsphere-e2e-operator

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 9, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 9, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/platform-none-vsphere-e2e-operator

In response to this:

/override ci/prow/platform-none-vsphere-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sebsoto
Copy link
Contributor

sebsoto commented Oct 9, 2025

/override ci/prow/ci-bundle-wmco-bundle ci/prow/images ci/prow/lint ci/prow/security ci/prow/unit

@sebsoto
Copy link
Contributor

sebsoto commented Oct 9, 2025

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator ci/prow/platform-none-vsphere-e2e-operator ci/prow/vsphere-proxy-e2e-operator ci/prow/vsphere-e2e-operator ci/prow/wicd-unit-vsphere ci/prow/vsphere-disconnected-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 9, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/ci-bundle-wmco-bundle, ci/prow/images, ci/prow/lint, ci/prow/security, ci/prow/unit

In response to this:

/override ci/prow/ci-bundle-wmco-bundle ci/prow/images ci/prow/lint ci/prow/security ci/prow/unit

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 9, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/aws-e2e-operator, ci/prow/azure-e2e-operator, ci/prow/azure-e2e-upgrade, ci/prow/gcp-e2e-operator, ci/prow/nutanix-e2e-operator, ci/prow/platform-none-vsphere-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator, ci/prow/vsphere-e2e-operator, ci/prow/vsphere-proxy-e2e-operator, ci/prow/wicd-unit-vsphere

In response to this:

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator ci/prow/platform-none-vsphere-e2e-operator ci/prow/vsphere-proxy-e2e-operator ci/prow/vsphere-e2e-operator ci/prow/wicd-unit-vsphere ci/prow/vsphere-disconnected-e2e-operator

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 4c00686 into openshift:release-4.18 Oct 9, 2025
18 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-62480: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-62480 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #3234

/assign sebsoto

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-cherrypick-robot
Copy link
Author

@sebsoto: new pull request created: #3446

In response to this:

/cherry-pick release-4.17 release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants